Asset Scans
Who should read these docs?
Firmware and software engineers working with asset scan data.
Asset scanning allows a connected device to report nearby Bluetooth tool detections to the platform. The platform parses each BLE advertisement, extracts tool identifiers, and submits the results to the Tool Location Service API. This powers last-known-location and proximity features in OneKey as well as other downstream systems that aggregate and parse product-specific extended advertisement data (read more).
Publishing Asset Scans
MQTT
Publish scan results to the following topic using QoS 0. Basic Ingest bypasses the MQTT broker message fee, which matters at the publishing rates typical of asset scanning.
$aws/rules/dt_asset_scan_ingest/dt/{MPBID}/asset_scan
HTTPS
If MQTT is not available or practical, scan results can be submitted over HTTPS using the Asset Scan Ingest REST API. Authentication uses the same mTLS device certificate as MQTT.
What happens next
After a message is published, two things happen in parallel:
-
Tool Location Services — the payload is validated, BLE advertisements are parsed to extract tool MPBIDs and location data, and the results are forwarded to the Tool Location Service to update each tool's last-known location. See Processing Pipeline for details.
-
Data lake archive — the raw message is written to an S3 data lake before processing, enabling replay and historical queries via Athena. See Processing Pipeline for details.
Prerequisites
The device must be fully provisioned before publishing asset scans. See Phase 2 Fleet Provisioning if provisioning is not yet complete.